We will expand our UI, and give the user the possibility to edit his wishlist. We will use the earlier defined actions. We also will use model clones only to modify data temporarily, and after approving the changes, apply them back to the original model.

In this lesson you will learn:

• How to call model actions from a component
• Using clone to create a full, deep clone of any model instance
• Using applySnapshot to update the state of a model instance given a snapshot.

 

The whole point for building a editing form component is that:

  1. avoid two ways data flow, means that you change the data inside the form, without saving but the data was mutated already. To solve this problem, we will use 'clone' from 'mobx-state-tree'.

  2. When save the data, we can use 'getSnapshot' and 'applySnapshot' from the lib.

import React, {Component} from "react"import {observer} from "mobx-react";import {clone, getSnapshot, applySnapshot} from 'mobx-state-tree';import WishListItemEdit from "./WishListItemEdit"class WishListItemView extends Component {    constructor() {        super();        this.state = {isEditing: false}    }    render() {        const {item} = this.props;        return this.state.isEditing ?            this.renderEditable() :            this.renderItemView(item);    }    renderEditable() {        return (            
                
                      
       ?                
       ❎            
      
        );    }    renderItemView(item) {        return (            
                {item.image && }                
{item.name}
                {item.price}                                    ✏                            
        );    }    onSaveEdit = () => {        applySnapshot(this.props.item, getSnapshot(this.state.clone))        this.setState({            isEditing: false,            clone: null        })    };    onCancelEdit = () => {        this.setState({isEditing: false})    };    onToggleEdit = () => {        this.setState({            isEditing: true,            clone: clone(this.props.item)        })    }}export default observer(WishListItemView)

 

Here we have to use the methods provide from the lib, because the 'this.props.item' is a mobx state model object:

{$mobx: ObservableObjectAdministration, toString: ƒ, …}

 

The good part of this approach is that, the model related data can be handled by the mobx-state-tree lib. It can helps to udpate the model efficiently.

The down side of the approach is that,  you needs to keep at least tow parts of state, one is mobx-state-tree, another one is the component state, for example, in the code, 'isEiditing' & 'clone'.